home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD ROM Paradise Collection 4
/
CD ROM Paradise Collection 4 1995 Nov.iso
/
hobby
/
gim_308.zip
/
GIM11D.DOC
< prev
next >
Wrap
Text File
|
1995-02-07
|
43KB
|
999 lines
CHAPTER 11 LISTS OF SIMILAR PERSONS, FAMILIES AND NOTES
OR
SEARCHING YOUR FOLDER FOR SPECIFIC INFORMATION
PART D: OPERANDS USED IN WHERE COMMANDS...
In this section we assume that you know what a WHERE command
is, how it's used, and what it's used for. We also assume
that you know what operators and operands in WHERE commands
are, and how they are used. If you haven't done so already,
review the first section in this chapter, which is entitled
"An Introduction with Basic Examples", and skim the section
entitled "Operators Used in WHERE Commands".
The WHERE command provides a number of operands. These can
be broken into two major categories, as follows:
1. Constants, such as "4 July 1776" or "George"
2. Variables, such as BIRTH DATE or SURNAME
We'll discuss constants first, because they can be explained
quickly. Then we'll turn our attention to the many variable
operands that are available, and discuss them each in detail.
CONSTANT OPERANDS:
Constant operands come in three flavors:
1. String constants, such as "Posen, Poland"
2. Numeric constants, such as 5, or 12
3. Date constants, such as 1776, or "4 Jul 1776"
We'll present each of these in turn.
STRINGS...
STRING CONSTANTS:
String constants must always be enclosed by quotation
marks, no matter whether the string constant is a single
word, or several words.
Examples of valid string constants:
"microfilm"
"George Washington"
"Durup, Viborg, Denmark"
"" -- but see note 3.
Examples of invalid string constants:
microfilm
George Washington
Durup, Viborg, Denmark
Examples of the correct use of string constants:
WHERE surname is "Washington"
WHERE any place contains "Czechoslovakia"
WHERE birth source note contains "microfilm"
Notes about the use of string constants:
1. String searches may be either CASE SENSITIVE or
CASE INSENSITIVE. "CASE SENSITIVE" means that
a search for "Poland" is quite different from a
search for "poland" or "POLAND".
Case sensitivity can be turned on or off; see
the section entitled "A Glossary of GIM LISTS
Commands with Examples", under the heading
CASESENS, for details.
2. The fact that string constants are delimited by
quotation marks means that string constants
cannot contain quotation marks. In other
words, it is not possible for to search for
this place name ...
ship "U.S.S. Wyoming"
... because the following construction is
illegal:
WHERE birth place is "ship "U.S.S. Wyoming""
To get around this, use some variation on the
following...
WHERE birth place contains "U.S.S. Wyoming"
... and then harass me until I get this fixed!
3. The string constant "" is legal, but it is best
avoided. The command ...
WHERE birth place contains ""
... is more clearly expressed as ...
WHERE birth place isn't missing
... and the command ...
WHERE birth place is ""
... is more clearly expressed as ...
WHERE birth place is missing
It is therefore best to avoid the use of ""
whenever possible.
NUMBERS...
NUMERIC CONSTANTS:
Unlike string constants, numeric constants must not be
enclosed by quotation marks.
Examples of valid numeric constants:
-5
12
14000000
Examples of invalid numeric constants:
"-5"
"12"
"14000000"
3.5 -- see note 1 below
1234123412341234123412341234 -- see note 2 below
Examples of the correct use of numeric constants:
WHERE spouses ge 2
WHERE children gt 5 and children lt 9
WHERE gin gt 0
Notes about the use of numeric constants:
1. Numeric constants must be integers. It should
never be necessary to use real numbers in WHERE
commands; if you find an exception, please let
me know!
2. Numeric constants must fall in the range of
integers from -2147483647 to 2147483647.
DATES...
DATE CONSTANTS:
Date constants should always be enclosed in quotation
marks. You may omit them if the date constant is a
single, four-digit number, representing a year, such as
1776. In this case, it doesn't hurt to include them.
In all other cases, they must be included.
Examples of valid date constants:
"30 Apr 1964"
"30 April 1964"
"4 Jul 1776"
"1776"
1776
Examples of invalid date constants:
3 March 1964 -- see note 1.
984 -- see note 2.
"infant" -- see note 4.
Examples of the correct use of date constants:
WHERE birth date is after "1 Mar 1881"
WHERE birth date is before 1500
WHERE marriage date is "15 Jun 1961"
Notes about the use of date constants:
1. As has been stated, any date constant that
isn't a simple year must be enclosed in
quotation marks.
2. If a date constant is a simple year, it must be
exactly four digits, or else it must be
enclosed in quotation marks.
3. If a date constant is a simple year, such as
1920, it is interpreted as a point in time
between 1919 and 1920. Therefore, searching
for dates ON OR BEFORE 1920 will NOT include
dates IN 1920; on the other hand, searching for
dates ON OR AFTER 1920 WILL include dates IN
1920. For this reason, unless you are being
deliberately general in your search, it is
always best to include a month and day in your
date constants, such as "31 Dec 1920".
4. As a matter of fact, "infant" is legal, but
meaningless. Date constants are used by date
operators to represent a point in time. The
constant "infant" is equivalent to "no time",
and results in unpredictable behavior. If you
want to compare dates with strings of charac-
ters, use string operators instead of date
operators. In that case, "infant" becomes a
legal string constant, rather than a date
constant; in that case, the value of "infant"
has meaning.
VARIABLES...
VARIABLE OPERANDS:
Variable operands come in three flavors:
1. Those that stand on their own, such as PIN, GIN,
SURNAME, SPOUSES, or AFN. These are the most basic
kind of variable operand, and take no modifiers.
These will be discussed below, in a section entitled
"Basic Variables".
2. Those that are modified with ANY or ALL, such as ANY
PLACE or ANY RESEARCH NOTE or ANY VITALS PLACE.
These are more involved, and will be discussed below
in a section entitled "Modifier Variables".
3. Those that point to other variables, such as MOTHER
or CHILD. These will require some explaining, which
will be done in a section below entitled "Pointer
Variables".
Each of these three flavors will be discussed in turn, in its
own subsection, after which all of the variable operands will
be presented in a diagram which should hopefully tie all of
this together.
BASIC VARIABLES...
Variables in this section are simple, one-word operands
that need little explanation.
Each operand in this section will be followed by four or
five lines of description, as follows:
List Type:
"Persons", "Families", "Notes", or "Persons and
Families", depending on which types of lists may be
created with this operand.
It doesn't make sense, for example, to use the PIN
or GIN operands, which are person-related operands,
when generating a list of families, so you will see
"List Type: Persons" beneath these operands.
However, the CHILDREN operator has meaning (albeit
a slightly different one in each case) for both
lists of Persons and lists of Families, so you will
see "List Type: Persons and Families" beneath
operands like this one.
Operand Type:
Date, Number, String, and/or Note, depending on
which type(s) of operator(s) make(s) sense with
this operand. It doesn't make sense, for example,
to use the "contains" operator, which is a string
operator, with the FIN operand, which is a number.
Meaning:
A summary in English of the concept that the
operand's name represents.
Example:
An example of the way the operand may be used.
Notes:
If there is anything potentially confusing or
unusual about the use of this operand, it will be
clarified here.
The basic variable operands are as follows:
AFN:
List Type: Persons
Operand Type: String
Meaning: The person's Ancestral File Number
Example: WHERE afn is "HRVP-BD"
CHILDREN:
List Type: Persons or Families
Operand Type: Number
Meaning: For persons:
The person's number of children by
all spouses
For families:
The family's number of children
Example: WHERE children ge 12
CODE:
List Type: Persons
Operand Type: String
Meaning: The person's "code" value.
Example: WHERE code isn't missing
FIN:
List Type: Families
Operand Type: Number
Meaning: The family's FIN number.
Example: WHERE FIN gt 1000
FIRST:
List Type: Persons
Operand Type: String
Meaning: The person's first name
Example: WHERE first is "Johannes"
Notes: 1. See also GIVEN, a synonym for FIRST.
2. FIRST takes on an entirely different
meaning when used as a modifier, as in
FIRST SPOUSE or FIRST CHILD. This usage
is described below, in the section
entitled "Modifier Variables".
FULL:
List Type: Persons
Operand Type: String
Meaning: The person's full name
Example: WHERE full is "George Washington"
GENDER:
List Type: Persons
Operand Type: String
Meaning: The person's gender as "M", "F", or "U"
Example: WHERE gender is "F"
GIN:
List Type: Persons
Operand Type: Number
Meaning: The person's GIN number
Example: WHERE GIN ne 0
GIVEN:
List Type: Persons
Operand Type: String
Meaning: The person's given name
Example: WHERE given contains "Maria"
Notes: See also FIRST, a synonym for GIVEN.
LAST:
List Type: Persons
Operand Type: String
Meaning: The person's last name
Example: WHERE last is "Smith"
Notes: 1. See also SURNAME, a synonym for LAST
2. LAST takes on an entirely different
meaning when used as a modifier, as in
LAST SPOUSE or LAST CHILD. This usage
is described below, in the section
entitled "Modifier Variables".
NOTE:
List Type: Notes
Operand Type: Note
Meaning: The note in a list of notes
Example: WHERE note contains "Error in the IGI:"
Notes: NOTE takes on an entirely different meaning
when used with modifiers, as in SOURCE NOTE
or RESEARCH NOTE. This usage is described
below, in the section entitled "Modifier
Variables".
NUMPARENTS:
List Type: Persons
Operand Type: Number
Meaning: The person's number of parents
Example: WHERE parents eq 1 or parents eq 3
Notes: NUMPARENTS counts parents separately. That
is, if a person has two *sets* of parents,
with a mother and father in each set, then
the total value of NUMPARENTS will be 4. If
a person has a father and no mother, or vice
versa, the value of NUMPARENTS will be 1.
NUMPARENTSETS:
List Type: Persons
Operand Type: Number
Meaning: The person's number of sets of parents
Example: WHERE parentsets gt 1
Notes: NUMPARENTSETS counts parents in sets. That
is, if a person has two *sets* of parents,
with a mother and father in each set, then
the total value of NUMPARENTSETS will be 2,
not 4. If a person has a father and no
mother, or vice versa, the value of
NUMPARENTSETS will be 1.
PIN:
List Type: Persons
Operand Type: Number
Meaning: The person's PIN number
Example: WHERE pin ge 4 and pin le 7
REFN:
List Type: Persons
Operand Type: String
Meaning: The person's reference number value
Example: WHERE refn contains "PAF"
SPOUSES:
List Type: Persons
Operand Type: Number
Meaning: The person's number of spouses
Example: WHERE spouses eq 2
SURNAME:
List Type: Persons
Operand Type: String
Meaning: The person's last name
Example: WHERE surname is "Smith"
Notes: See also LAST, a synonym for SURNAME
MODIFIER VARIABLES...
Variables in this section are used to express thoughts
like "any place" or "first marriage date" or "all source
notes". They can also get a little more involved, and
can be used to express thoughts like:
* any LDS ordinance date
* all non-LDS, vital statistics places
* any marriage's research notes
This section will explain how to translate these
thoughts into GIM LISTS variable operands.
In order to do so, we first need to define three groups,
called GROUP A, GROUP B, and GROUP C. Modifier
variables such as BIRTH and MARRIAGE are applied to
members of some or all of these groups.
Let's define them first, before we go on:
GROUP A: DATE, PLACE, PLACEBEG or PLACEEND
DATE:
Operand Type: Date
When the word "DATE" is used together with
preceding keywords, like MARRIAGE or BIRTH,
it represents the marriage date of a given
family, or the birth date of a given person.
PLACE:
Operand Type: String
When the word "PLACE" is used together with
preceding keywords, like MARRIAGE or BIRTH,
it represents the marriage place of a given
family, or the birth place of a given person.
PLACEBEG:
Operand Type: Date
This operator only makes sense with LDS events
(baptism, endowment, and sealings). When used
together with preceding keywords, like SEALSP
or ENDOWMENT, it represents the date that this
event's temple opened. For more details, see
the section entitled "Advanced Examples;
Arcane WHERE Command Syntax".
PLACEEND:
Operand Type: Date
This operator only makes sense with LDS events
(baptism, endowment, and sealings). When used
together with preceding keywords, like SEALSP
or ENDOWMENT, it represents the date that this
event's temple closed. For more details, see
the section entitled "Advanced Examples;
Arcane WHERE Command Syntax".
GROUP B: NOTE
Operand Type: Note
In certain cases, usually with ANY or ALL, it is
legal to refer to a "note" without specifying
whether you mean a source or a research note.
GROUP B should be thought of as a special case of
GROUP C, discussed below.
GROUP C: SOURCE NOTE or RESEARCH NOTE
SOURCE NOTE:
Operand Type: Note
When the words "SOURCE NOTE" are used together
with preceding keywords, like MARRIAGE or
BIRTH, they represent the marriage source note
of a given family, or the birth source note of
a given person.
RESEARCH NOTE:
Operand Type: Note
When the words "RESEARCH NOTE" are used to-
gether with preceding keywords, like MARRIAGE
or BIRTH, they represent the marriage research
note of a given family, or the birth research
not of a given person.
Now we'll list the variable operands that modify each of
these groups. In these listings, the categories "List
Type", "Meaning", "Example" and "Notes" mean what they
did in the "Basic Variables" section above. The
"Operand Type" category has been moved to the GROUP
definitions above, and a new category has been added;
the category "Followed by" means that a member of the
listed GROUPs may follow the listed operand.
BAPTISM:
List Type: Persons
Followed by: GROUP A, GROUP C
Meaning: The person's LDS baptism event
Example: WHERE baptism source note contains "Living"
BIRTH:
List Type: Persons
Followed by: GROUP A, GROUP C
Meaning: The person's birth event
Example: WHERE birth date is after 1945
BURIAL:
List Type: Persons
Followed by: GROUP A, GROUP C
Meaning: The person's burial event
Example: WHERE burial date is before death date
CHRISTENING:
List Type: Persons
Followed by: GROUP A, GROUP C
Meaning: The person's christening event
Example: WHERE christening date is birth date
DEATH:
List Type: Persons
Followed by: GROUP A, GROUP C
Meaning: The person's death event
Example: WHERE death date is burial date
ENDOWMENT:
List Type: Persons
Followed by: GROUP A, GROUP C
Meaning: The person's LDS endowment event
Example: WHERE endowment place contains "New Zealand"
GENERAL:
List Type: Persons or Families
Followed by: GROUP C
Meaning: Person's or Family's miscellaneous notes
Example: WHERE general source note contains "SSN"
MARRIAGE:
List Type: Persons or Families
Followed by: GROUP A, GROUP C
Meaning: For persons:
The person's "selected" marriage
event; see chapter 4 for details
For families:
The family's marriage event
Example: WHERE marriage date is sealsp date
SEALPAR:
List Type: Persons
Followed by: GROUP A, GROUP C
Meaning: The person's LDS sealing to parents event
Example: WHERE sealpar place contains "New Zealand"
SEALSP:
List Type: Families
Followed by: GROUP A, GROUP C
Meaning: For persons:
The person's "selected" sealing to
spouse event; see chapter 4 for
details
For families:
The family's sealing to spouse event
Example: WHERE sealsp place contains "New Zealand"
Now, we can modify these variables even more, by using
modifiers like "ANY" and "ALL", to select "any place" or
"all dates".
There are five of these modifiers:
ANY: Select any member of the group
ALL: Select all members of the group
FIRST: Select the first member of the group
NUMBER #: Select the #th member of the group
LAST: Select the last member of the group
These may be used in any of five different situations:
ANY/ALL VITAL:
This situation applies only to lists of
persons.
"VITAL" events are non-LDS vital statistics;
specifically, birth, christening, death,
burial, and any and all marriages.
We can combine ANY or ALL with VITAL to select
these vital statistics. For example ...
MAKE Germans
FROM All Persons
WHERE any vital place contains "Germany"
... will select any persons who have "Germany"
in their vital statistics, no matter whether
that place name is in the birth, or death, or
one of their marriages. By contrast, this ...
WHERE all vital places contain "Germany"
... requires that ALL of the vital statistics
places must contain the word "Germany" (or be
empty).
Note that VITALS and VITAL may be used inter-
changeably, and so can PLACE and PLACES. This
helps keeps WHERE commands from sounding
awkward.
ANY/ALL LDS:
This situation applies only to lists of
persons.
This situation is just like ANY/ALL VITALS
above, except that it refers only to the LDS
events: baptism, endowment, sealing to
parents, and any and all sealings to spouses.
For example, this ...
WHERE any lds place doesn't contain "Temple"
... selects LDS places outside of temples,
such as living baptisms or Endowment House
sealings.
ANY/ALL/FIRST/NUMBER/LAST MARRIAGE:
This situation applies only to lists of
persons.
This situation is just like ANY/ALL VITALS
above, except that it only refers to the set
of any and all of a person's marriages.
For example, this ...
WHERE death date is before first marriage date
... selects persons who died before their
first marriage.
ANY/ALL/FIRST/NUMBER/LAST SEALSP:
This situation applies only to lists of
persons.
This situation is just like ANY/ALL LDS above,
except that it only refers to the set of any
and all of a person's sealings to spouses.
ANY/ALL:
This situation applies only to lists of
families.
This situation refers to the marriage and
sealing to spouse event, taken together.
In other words, the command ...
MAKE Microfilms
FROM All Families
WHERE any source note contains "microfilm"
... will select families if the word microfilm
appears in either the marriage source note or
in the sealing to spouse source note. By
contrast, this ...
WHERE all source notes contain "microfilm"
... will select families if the word microfilm
appears in BOTH the marriage source note AND
in the sealing to spouse source note.
POINTER VARIABLES...
Variables in this section are potentially confusing, and
they may take some time to fully understand. However,
they serve an important, useful and powerful function,
and you will thank me for encouraging you to spend time
learning about them.
Suppose you are searching through the list of All
Persons for persons with the name "David". You would do
that with the following set of GIM LISTS commands:
MAKE Davids
FROM All Persons
WHERE full contains "David"
(or, WHERE given is "David"; take your pick....)
But, what if you want to find all the people whose
FATHER's name was David? To do this, use the FATHER
operand; anything after the FATHER operand can be any
operand that relates to persons. Specifically:
MAKE David's Children
FROM All Persons
WHERE father full contains "David"
Take a moment and reflect on the power of this simple
keyword. I mean it. Really. Stop right now and give
it some thought. You'll thank me for it.
It means that you can search for anything about a
person's parents that you can search for about a person.
In fact, you can search for anything about a person's
parents' parents that you can search for about a person.
For example, to find all grandchildren of men named
David, use this command:
MAKE David's Grandchildren
FROM All Persons
WHERE father father full contains "David" or
mother father full contains "David"
For this reason, the FATHER keyword in the list below
has "Persons" after "Followed by:". It means that when
you use the operand FATHER, you can follow it with any
person-related operand, such as BAPTISM DATE or PIN or
GIN or FIRST SPOUSE or whatever.
Similarly, if "Followed by:" is followed by "Families",
such as is the case with the FAMILY operand, you can
follow that operand with any family-related operand.
This is important to understand, because a person's
marriage information is not accessible without it. In
other words, "WHERE marriage date is missing" is legal
for families, but not for persons. To get a person's
marriage date, use "WHERE any family marriage date is
missing".
In this list, we add a new entry in the description
list, called "ANY/ALL Modifiers:"
"ANY/ALL Modifiers: Yes" means that any of the "ANY,
ALL, FIRST, NUMBER #, and LAST" modifiers, which were
discussed in the foregoing subsection (entitled
"Modifier Variables") can be used here. Their use is
optional.
"ANY/ALL Modifiers: No" means that the ANY, ALL, FIRST,
NUMBER #, and LAST modifiers are meaningless in
connection with this operand.
CHILD:
List Type: Families
ANY/ALL Modifiers: Yes
Followed by: Persons
Meaning: One, some, or all of the family's
children, depending on which modifier
precedes this one.
Example: WHERE any child afn is missing
Notes: When CHILD is not preceded by modifier such
as ANY, ALL, etc., and when there are
several children to choose from, GIM LISTS
assumes the "progenitor" child; see chapter
8 for details.
FAMILY:
List Type: Persons
ANY/ALL Modifiers: Yes
Followed by: Families
Meaning: One, some, or all of the person's
families, depending on which modifier
precedes this one.
Example: WHERE family general source note contains "X"
Notes: When FAMILY is not preceded by a modifier
such as ANY, ALL, etc., and when there are
several to choose from, GIM LISTS assumes
the "selected" spouse's family; see chapter
4 for details.
FATHER:
List Type: Persons or Families
ANY/ALL Modifiers: No
Followed by: Persons
Meaning: The person's father,
or the family's husband
Example: WHERE surname isn't father surname
Notes: See also HUSBAND, which is a synonym for
FATHER, but only when used for lists of
families.
HUSBAND:
List Type: Families
ANY/ALL Modifiers: No
Followed by: Person
Meaning: The family's husband
Example: WHERE husband gin ne 0
Notes: See also FATHER, which is a synonym for
HUSBAND.
MOTHER:
List Type: Persons or Families
ANY/ALL Modifiers: No
Followed by: Persons
Meaning: The person's mother,
or the family's wife
Example: WHERE mother gin isn't 0
Notes: See also WIFE, which is a synonym for
MOTHER, but only when used for lists of
families.
PARENTS:
List Type: Persons
ANY/ALL Modifiers: No
Followed by: Families
Meaning: The person's parents.
Example: WHERE parents marriage date isn't missing
Notes: To be consistent, PARENTS should take ANY
and ALL modifiers, for persons with multiple
sets of parents. Look for this to be added
in a future release. For now, if there are
multiple parents, only the "selected" or
principal set of parents is used.
SPOUSE:
List Type: Persons
ANY/ALL Modifiers: Yes
Followed by: Persons
Meaning: One, some, or all of the person's
spouses, depending on which modifier
precedes this one.
Example: WHERE spouse gin ne 0
Notes: When SPOUSE is not preceded by an operand,
and when there are several to choose from,
GIM LISTS assumes the "selected" spouse;
see chapter 4 for details.
WIFE:
List Type: Families
ANY/ALL Modifiers: No
Followed by: Person
Meaning: The family's wife
Example: WHERE wife gin ne 0
Notes: See also MOTHER, which is a synonym for
WIFE.
THE DIAGRAM...
If you've followed me so far -- which I admit is not an easy
feat! -- the following diagram should help to put all of the
pieces together. If it's not completely obvious and clear to
you, after you've read the foregoing discussion, please let me
know what doesn't make sense.
GLOBAL ABBREVIATIONS:
┌───┐ ┌ ┐ ┌───┐ ┌ ┐ ┌ ┐
│ A │ ──> │ DATE │ │ C │ ──> │ SOURCE │ ──> │ │
└───┘ │ PLACE │ └───┘ │ RESEARCH │ │ │
│ PLACEBEG │ └ ┘ │ │
│ PLACEEND │ │ NOTE │
└ ┘ ┌───┐ │ │
│ B │ ──> │ │
└───┘ │ │
└ ┘
< ... > == nothing, meaning only, or skip if none, or selected (p.select
for spouses or f.progenitor for children) if multiple
CONSTRUCTIONS FOR PERSONS:
┌ ┐
┌ ┐ │ VITAL │ ┌ ┐
┌──> │ ANY │ ──> │ LDS │ ──> │ A │
│ │ ALL │ └ ┘ │ B │
│ └ ┘ ────────────────> │ C │
│ └ ┘
│ ┌ ┐
│ ┌ ┐ │ A │
│ │ MARRIAGE │ ──> │ B ┼> { B only if ANY or ALL }
│ ┌ ┐ ──> │ SEALSP │ │ C │
│ │ ANY │ └ ┘ └ ┘
│ │ ALL │ ┌ ┐
├──> │ FIRST │ ──> │ FAMILY │ ──> Family
│ │ < ... > │ └ ┘
│ │ NUMBER # │ ┌ ┐
│ │ LAST │ ──> │ SPOUSE │ ──> Person
│ └ ┘ └ ┘
│
│ ┌ ┐ ┌ ┐
├──> │ GENERAL │ ──> │ C │
│ └ ┘ └ ┘
│
│ ┌ ┐
Person ───┼──> │ FATHER │ ──> Person
│ │ MOTHER │
│ └ ┘
│
│ ┌ ┐
├──> │ PARENTS │ ──> Family
│ └ ┘
│
│ ┌ ┐
│ │ BIRTH │
├──> │ CHR │ ┌ ┐
│ │ DEATH │ │ A │
│ │ BURIAL │ ──> │ │
│ │ BAPT │ │ C │
│ │ ENDOW │ └ ┘
│ │ SEALPAR │
│ └ ┘
│
│ ┌ ┐
│ │ AFN │
│ │ REFN │
│ │ PIN │
│ │ GIN │
│ │ FIRST or GIVEN │
│ │ LAST or SURNAME │
│ │ FULL │
└──> │ CODE │
│ NUMPARENTS │
│ NUMPARENTSETS │
│ SPOUSES │
│ CHILDREN │
│ GENDER │
└ ┘
CONSTRUCTIONS FOR FAMILIES:
┌ ┐
┌ ┐ │ A │
┌──> │ ANY │ ──> │ B │
│ │ ALL │ │ C │
│ └ ┘ └ ┘
│
│ ┌ ┐
│ │ ANY │
│ │ ALL │ ┌ ┐
├──> │ FIRST │ ──> │ CHILD │ ──> Person
│ │ < ... > │ └ ┘
│ │ NUMBER # │
│ │ LAST │
│ └ ┘
│
│ ┌ ┐ ┌ ┐
Family ───┼──> │ GENERAL │ ──> │ C │
│ └ ┘ └ ┘
│
│ ┌ ┐
│ │ FATHER │
├──> │ HUSBAND │ ──> Person
│ │ MOTHER │
│ │ WIFE │
│ └ ┘
│
│ ┌ ┐
│ ┌ ┐ │ A │
├──> │ MARRIAGE │ ──> │ │
│ │ SEALSP │ │ C │
│ └ ┘ └ ┘
│
│ ┌ ┐
│ │ FIN │
└──> │ CHILDREN │
└ ┘
CONSTRUCTIONS FOR NOTES:
┌ ┐
Note ──────> │ B │
└ ┘
